-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the issue template for creating release branches #677
Update the issue template for creating release branches #677
Conversation
4ffd2c9
to
462d66f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, only minor comments/questions
@@ -89,7 +89,7 @@ The steps are to be followed in-order, each task must be completed by the person | |||
- [ ] **Owner**: Create `release-1.xx` branch from latest `main` in rawfile-localpv | |||
- `git clone [email protected]:canonical/rawfile-localpv.git ~/tmp/release-1.xx` | |||
- `pushd ~/tmp/release-1.xx` | |||
- `git switch main` | |||
- `git switch rockcraft` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
huh? Why do we have this weird main branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the "default" branch of the rawfile-localpv b/c this is a forked repo and rather than working out of main (as the upstream author does) we do our work out of the rockcraft branch. We're trying to get the rockcraft work upstreamed...
so for the moment "OUR" main is rockcraft
462d66f
to
7e68087
Compare
Overviews the release template
Based on #666 , improved the process to create release branches